Full mesh status monitor

ABSTRACT

A method for verifying full mesh status in a network is disclosed. The network includes endpoint entities in full mesh configuration. The method includes a step of maintaining a first value in the endpoint entities. The first value is related to counting of network endpoint entities. Another step in the method is maintaining a second value in the endpoint entities. The second value is related to counting non-operational transmission paths before a point in time. An additional step in the method is discovering an additional value related to counting non-operational transmission paths after the point in time. Yet another step in the method is comparing the additional value with the first value and the second value.

FIELD OF THE INVENTION

This invention relates to a mechanism for monitoring full mesh status ina network and, in particular, improved auto-discovery within a networkof full mesh configured forwarders.

BACKGROUND OF THE INVENTION

Reference will be made in this application to layer-2. Layer-2 issometimes called the link layer. In addition to the link layer, thereare other layers including the network layer, the physical layer and theoptical layer. The traditional role of layer-2 is switching. Layer-2services (such as frame relay, ATM, Ethernet) can be emulated over anInternet Protocol (IP) or Multi-Protocol Label Switching (MPLS) backboneby encapsulating the layer-2 packet data units (PDUs) and thentransmitting them over pseudo-wires.

Virtual private local area network (LAN) service (VPLS) is anInternet-based multipoint-to-multipoint layer-2 virtual private network(L2VPN). With VPLS, multiple Ethernet LAN sites can be interconnected toeach other across an MPLS backbone. To the customer, all sites that areinterconnected by VPLS appear to be on the same Ethernet LAN (eventhough traffic travels across a service provider network).

VPLS interconnects a set of VPLS forwarders. VPLS forwarders are virtualentities inside provider edge devices (PEs). For a given VPLS instance,there is one VPLS forwarder in a given PE. Some of the forwarders areconsidered “spokes”, and some are considered “hubs”. In a given VPLSinstance, there must be pseudo-wire binding every hub VPLS forwarder toevery other hub VPLS forwarder. This means that every hub PE in the VPLSinstance must have a pseudo-wire to each other hub PE in the VPLSinstance. When this condition holds, we say that the VPLS instance isfully meshed. When the VPLS PEs are fully meshed, every ingress PE cansend a VPLS packet to egress PE(s) directly, without the need for anintermediate PE.

It is possible that a given VPLS instance may fail to be fully meshed.This may happen for the following reasons: configuration errors, failureof the auto-discovery process, failure of the control plane to properlyestablish all the necessary pseudo-wires (this in turn may be due tobugs, or to resource shortages at the PEs), and failure of the dataplane to carry traffic correctly on all established pseudo-wires (thiscan occur if there are bugs in the capsulation/de-capsulation proceduresat the PEs or bugs in the forwarding procedures at intermediate nodes).

If a VPLS instance is not fully meshed, then it will not provide theLAN-like service over which its users are depending. For instance, if alink state routing algorithm is using its LAN procedures over a VPLSinstance which is not fully meshed, the selected set of routes may have“black holes”.

Therefore there needs to be a mechanism in the emulated LAN to identifythe falling out of full mesh status, so that appropriate steps can betaken to restore the full mesh. One known mechanism is to runSpanning-Tree Protocol (STP) over each emulated LAN pseudo-wire. Thismethod has scaling problems because of the number of Bridge ProtocolData Units (BPDUs) that need to be sent by each VPLS forwarder.

Another known method involves each VPLS forwarder having a list of otherVPLS forwarders. In addition, each VPLS forwarder has a list of VPLSforwarders with which it has established operational pseudo-wires.Identifying whether or not the full mesh status exists involvescomparing the two lists. This method also has scaling problems becauseit requires knowing the identifiers of all the VPLS forwarders. Also thelist may not be discovered at once, since the discovery can be anincremental process.

SUMMARY OF THE INVENTION

An object of the present invention is to provide an improved full meshstatus monitor.

According to a first aspect of the present invention, there is discloseda method for verifying full mesh status in a network, the networkincluding endpoint entities in full mesh configuration, the methodincluding the steps of:

maintaining a first value in the endpoint entities, the first valuebeing related to counting of network endpoint entities;

(2) maintaining a second value in the endpoint entities, the secondvalue being related to counting non-operational transmission pathsbefore a point in time;

(3) discovering an additional value related to counting non-operationaltransmission paths after the point in time; and

(4) comparing the additional value with the first value and the secondvalue.

According to another aspect of the invention, there is disclosed anetwork. The network includes transmission paths and at least twoendpoint entities configured for full mesh connectivity. Theconnectivity is provided by the transmission paths. The network alsoincludes an auto-discovery mechanism incorporating endpoint entity countinformation and status information of the transmission paths. Theauto-discovery mechanism facilitates reporting of full mesh status.

According to-yet another aspect of the invention, there is disclosed amethod for an endpoint entity to recognize that an associated emulatedLAN is down. The method includes the steps of:

maintaining full mesh status information in the endpoint entity thatindicates the emulated LAN is up;

(2) discovering newer full mesh status information that indicates theemulated LAN is down; and

(3) comparing said newer full mesh status information to said full meshstatus information, and then the endpoint entity recognizes the emulatedLAN has changed to a down state.

In one embodiment of this method, the newer full mesh status informationis discovered using an auto-discovery mechanism. The auto-discoverymechanism includes a TLV related to counting non-operationaltransmission paths.

An advantage of the present invention is that it reduces scalingproblems and improves emulated LAN restoration times.

Another advantage of the present invention is that it does not requireevery endpoint entity to maintain a list of all endpoint entities andtheir identifiers.

Yet another advantage of the present invention is that it reduces theneed to capture operations status in discovery.

Further features and advantages will become apparent from the followingdetailed description taken in conjunction with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a VPLS provider edge device.

FIG. 2 is a diagram illustrating a network reference model withpseudo-wires extending between provider edge devices.

FIG. 3 is a flow diagram illustrating operations within a VPLS forwarderbased on a discovered value related to counting operational transmissionpaths.

DETAILED DESCRIPTION

In this application, reference will be made to certain text files (i.e.,files having the filename extension “txt”). These are lnternet-Draftdocuments which have been published on the Internet Engineering TaskForce web site (ietf.org).

Referring to FIG. 1, there is illustrated a VPLS PE 10. Within the PE 10is a VPLS forwarder 14 which is connected to pseudo-wires 18. Theforwarder 14 has several functions, and it includes an operational stateidentifier, a discovery related component, a signaling related componentand an encapsulation related component. The forwarder 14 is configuredfor full mesh connectivity.

With respect to the pseudo-wires 18, each of the pseudrnwires 18 can bethought of as connecting the forwarder 14 to another forwarder. Howeverif the forwarder 14 is not a part of the same VPLS as another forwarder,then there will be no pseudo-wire 18 between the forwarder 14 and thatother forwarder. The pseudo-wires 18 provide the full mesh connectivityif they are all in an UP state. Protocol used to set up each of thepseudo-wires 18 must allow a forwarder at one end of the pseudo-wire toidentify the forwarder at the other end. Pseudo-wires are described indetail in “Pseudowire Setup and Maintenance using LDP”, Martini, et al.,available at ietf.org, the entire contents of which are incorporatedherein by reference.

If all of the pseudo-wires 18 are operational, then the VPLS forwarder14 considers emulated LAN 22 to be in an UP state. If even one of thepseudo-wires 18 is in a DOWN state, the emulated LAN 22 is alsoconsidered to be in a DOWN state.

The emulated LAN 22 communicates its operational status (UP/DOWN) to anupper layer. To facilitate this, an emulated LAN interface 26 isprovided so that the forwarder b can interface with bridge 30. Thebridge 30 is within the PE 10, but outside of the emulated LAN 22. Thebridge 30 does MAC address learning on the attachment circuits (ACs).The bridge 30 also does MAC address learning on the emulated LANinterface 26, but does not do MAC address learning on the pseudo-wiresb, as the pseudo-wires 18 are hidden behind the emulated LAN interface26.

Several definitions of the term bridge can be considered.

Definition 1; a bridge is a combination of hardware and software thatconnects LANs together.

Definition 2; a bridge is any device that connects two physicallydistinct network segments.

Definition 3; a bridge is a device that connects two similar LANs.

Typically, bridges transfer data in packets between two networks,without making any changes or interpreting the data in any way. Withrespect to the bridge 30, it must (at a minimum) be able to learn MediaAccess Control (MAC) addresses, and age MAC addresses out.

There is a link management protocol for the bridge 30. One possible linkmanagement protocol is STP. STP is a layer-2 protocol. STP defines atree that spans all bridges/switches in an extended network. STP forcescertain redundant data paths in a stand-by (locked) state. If onenetwork segment in STP becomes unreachable, or if STP costs change, thespanning-tree algorithm reconfigures a spanning-tree topology andreestablishes a link by activating the stand-by path.

At the commencement of a spanning-tree operation, the execution of thespanning-tree algorithm causes the bridges/switches to elect a singlebridge/switch, among all the bridges/switches within each network, to bethe root bridge/switch. The root bridge/switch is the logical centre ofthe spanning-tree topology in a switch network. All paths that are notneeded to reach the root bridge/switch from anywhere in the switchnetwork are placed in STP backup mode.

All bridges/switches in extended LAN participating in STP gatherinformation on other bridges/switches in a network through an exchangeof data messages. These messages are called Bridge Protocol Data Units(BPDUs). BPDUs contain information about the transmitting bridge/switchand its ports, including switch and port MAC addresses, switch priority,port priority, and port costs. The STP uses this information to electthe root bridge/switch and root port for the switch network, as well asthe root port and designated port for each switch segment.

A BPDU exchange results in the following. Firstly, one bridge/switch isselected as the root bridge/switch. Secondly, the shortest distance tothe root bridge/switch is calculated for each bridge/switch. Thirdly, adesignated bridge/switch is selected. This is the bridge/switch closestto the root bridge/switch through which frames will be forwarded to theroot. Fourth, a port for each bridge/switch is selected. This is theport providing the best path from the bridge/switch to the rootbridge/switch. Fifth, ports included in the STP are selected. Each porton a bridge/switch using STP exists in one of the following five states:blocking, listening, learning, forwarding and disabled.

The VPLS architecture associated with the provider edge deviceillustrated in FIG. 1 can be termed edge-to-edge MPLS. in thisarchitecture, MPLS is deployed all the way between service provideredges. There are also decoupled models. In a decoupled model, there isan access network between the VPLS forwarder 14 and the emulated LANinterface 26. The VPLS forwarder 14 is in one provider edge device(network-facing PE or N-PE), and the bridge 30 is in a differentprovider edge device (user-facing PE or U-PE). Decoupled TLS (see K.Kompella, et al. “Decoupled Virtual Private LAN Services”, InternetEngineering Task Force PPVPN Working Group, Internet Draft, November2002), Hierarchical VPLS (see M. Lasserre, et al. “Virtual Private LANServices over MPLS”, Internet Engineering Task Force ProviderProvisioned VPN Working Group, Internet Draft March 2003), Logical PE(see D. Mohan, et al. “VPLS/LPE L2VPNs: Virtual Private LAN Servicesusing Logical PE Architecture”, Internet Engineering Task Force ProviderProvisioned VPN Working Group, Internet Draft, March 2002) and GVPLS(see V. Radocac, et al., “GVPLS/LPE-Generalized VPLS Solution based onLPE Framework”, Internet Engineering Task Force Provider Provisioned VPNWorking Group, Internet Draft, June 2003) are examples of decoupled VPLSarchitectures.

In FIG. 2, Ethernet LANs 34 are connected together through the emulatedLAN. Within the Ethernet LANs 34 are one or more client edge devices(CEs) 38. The CEs 38 can include hosts, routers and/or bridges. Atransmission path 42 is provided between the bridge 30 and the CE 38.The transmission path 42 is within what is referred to as ACs. In anytype of L2VPN, AC is a circuit or virtual circuit that attaches a CE toa PE.

The pseudo-wires 18 extend across service provider network b (thenetwork 50 is an MPLS and/or IP network). When the PE b receives a PDUon a particular AC, it must determine the pseudo-wire 18 on which thePDU must be forwarded. In general, this is done by considering theincoming AC, possibly the contents of the PDU's layer-2 header, andforwarding information. Similarly, when the PE 10 receives a PDU on aparticular pseudo-wire, it must determine the AC on which the PDU mustbe forwarded. This is done by considering the incoming pseudo-wire,possibly the contents of the PDU's layer-2 header, and possibly someforwarding information which may be statically or dynamicallymaintained.

There is a general formula associated with the configuration illustratedin FIG. 2. Assuming there are n forwarders all belonging to a particularVPLS instance, there will be n-1 pseudo-wires for each forwarder, andthere will be (n-1)! pseudo-wires in total.

Applying the formula, there are four of the forwarders 14. Therefore(assuming a single VPLS instance) there are 4-1 (or 3) pseudo-wires foreach of the forwarders 14. The total number of the pseudo-wires 18 is 3!(or 6). It will be appreciated that the total number of the pseudo-wires18 will be large for all but single digit numbers of the forwarders 14.For example, if there are 10 of the forwarders 14, then the total numberof the pseudo-wires 18 is 9! (or 362,880). Scaling thus becomes an issuebecause of the BPDU volume potential.

A method in accordance with an embodiment of the present invention willnow be described. First, each VPLS forwarder is configured or discoversthe number of VPLS forwarders making up the emulated LAN 22. A firstvalue VFN will be maintained in each of the VPLS forwarders 14. VFNequals the number of the VPLS forwarders b making up the emulated LAN 22less 1. This is fitting (recall the n-1 formula discussed previously). Achange to VFN changes the operational status of the emulated LAN to DOWNfor a period of time.

VFN can be configured, or distributed using an auto-discovery mechanism.VFN can be incrementally learnt if we assume that the provider network50 will allow a given time t for discovery to run its course. It will beappreciated by one skilled in the art that VFN distribution can bedecoupled from the auto-discovery mechanism.

Each of the forwarders 14 also maintains a second value VFA. VFA is acount of the pseudo-wires 18 which are in a DOWN state. Therefore VFAwill equal 0 when all the pseudo-wires 18 are UP. Thus, when VFA equals0 the emulated LAN is considered UP. When VFA does not equal 0 theemulated LAN is considered DOWN. It is important to note that VFA needsto be distributed through discovery even when VFA is pre-configured. Adiscovered VFA value (DVFA) needs to be compared to the configured VFA.DVFA is a value in addition to the VFN and VFA values. When a DVFA isreceived by a particular forwarder, that DVFA will relate to a count ofnon-operational pseudo-wires at a later point in time than the countassociated with the VFA that the DVFA will be compared to.

The method for verifying full mesh status thus includes maintaining VFNand VFA values in the forwarders 14. The method also includes the stepsof discovering DVFA, and comparing that DVFA with the VFN and VFA valuesin the forwarders 14.

Addition or deletion of VPLS forwarders impacts the VFN and VFA values.When a new VPLS forwarder joins the full mesh, the new VPLS forwarderwill distribute its new VFN number (which is DVFA). Similarly when oneof the forwarders 14 is removed, the VFN is decremented and a new valueis advertised.

FIG. 3 is a flow chart illustrating operations which are performed whenthe forwarder 14 receives the DVFA. At step 60 operations commence. Atstep 62, the forwarder 14 tests if the DVFA value has been received. Ifit has not, the forwarder 14 continues its waiting to receive the DVFAvalue. If the DVFA value has been received, the operation proceeds tostep 64 and comparison operations are performed. The new full meshstatus information contained in the DVFA value is compared to the fullmesh status information maintained in the forwarder 14.

At step 68 a test is made on the results of the comparison operations ofstep 64. If a change to the full mesh status information is required theprocess proceeds to step 76. If no change is not required, the next stepis to conclude this round of the process at “End” step 72.

At step 76, operations are performed to change the full mesh statusinformation. A selected one of VFN, VFA, and VFN and VFA will be updatedat the step 76. It will be appreciated that proceeding to step 76 may bethe consequence of not only bugs/errors in one or more of thepseudo-wires 18, but also other alternative occurrences includingaddition of a VPLS forwarder and removal of a VPLS forwarder. Uponcompletion of step 76 this round of the process concludes at “End” step72.

VPLS auto-discovery is described in detail in “Framework for Layer 2Virtual Private Networks (L2VPNs)”, Andersson, et al., available atietf,org, the entire contents of which are incorporated herein byreference. In order for the VPLS auto-discovery mechanism to be able tofacilitate reporting of full mesh status, there will need to be anaddition of a type-length-value (TLV) element for the DVFA to the VPLSauto-discovery mechanism.

As explained previously, forwarder count information and statusinformation of the pseudo-wires can be furnished by the DVFA. Thus theVPLS auto-discovery mechanism with the additional TLV will beincorporating forwarder count information and status information of thepseudo-wires.

In one particular embodiment of the invention, a total number of VPLSforwarders (TVF) is maintained in each of the VPLS forwarders 14. TheTVF is the number of VPLS forwarders discovered plus 1. The TVF allowsthe VFN to be corrected in the situation where new VPLS forwarders areadded concurrently, and a PE receives the same DVFA which does notreflect the total number of VPLS forwarders.

It will be appreciated that the embodiment of the invention described inconjunction with FIGS. 1 and 2 is an embodiment of the inventionsuitable for VPLS. In more general nomenclature, the forwarders 14 areendpoint entities. For example, in an alternative embodiment of theinvention, the LAN service is IP-only LAN-like service (IPLS) instead ofVPLS. In this embodiment of the invention, the endpoint entities areCEs.

Transmission paths between the forwarders 14 have been characterized aspseudo-wires, and this term has a somewhat narrow meaning in Internetengineering. It will be appreciated by one skilled in the art that thereare other types of transmission paths over a service provider networkbesides pseudo-wires.

Glossary of Acronyms Used

AC—Attachment Circuit

BPDU—Bridge Protocol Data Unit

CE—Client Edge Device

IP—Internet Protocol

IPLS—IP-only LAN-like Service

L2VPN—Layer-2 Virtual Private Network

LAN—Local Area Network

MAC—Media Access Control

MPLS—Multi-Protocol Label Switching

N-PE—Network-Facing PE

PDU—Packet Data Unit

PE—Provider Edge Device

STP—Spanning-Tree Protocol

TLV—Type-Length-Value

U-PE—User-Facing PE

VPLS—Virtual Private LAN Service

Numerous modifications, variations and adaptations may be made to theparticular embodiments of the invention described above withoutdeparting from the scope of the invention, which is defined in theclaims.

1. A network comprising: transmission paths; at least two endpointentities configured for full mesh connectivity, said connectivity beingprovided by said transmission paths; and an auto-discovery mechanismincorporating endpoint entity count information and status informationof said transmission paths, wherein said auto-discovery mechanismfacilitates reporting of full mesh status.
 2. A network as claimed inclaim 1 wherein said auto-discovery mechanism includes aType-Length-Value element related to counting non-operationaltransmission paths.
 3. A network as claimed in claim 2 furthercomprising provider edge devices, each of said at least two endpointentities being within a different one of said provider edge devices. 4.A network as claimed in claim 3 wherein said endpoint entities areforwarders, and said transmission paths are pseudo-wires.
 5. A networkas claimed in claim 4 wherein each of said provider edge devicesincludes a bridge and an emulated Local Area Network interface, saidemulated Local Area Network interface permitting said bridge tointerface with one of said forwarders, said bridge being capable ofcommunicating with client edge devices.
 6. A network as claimed in claim5 further comprising Bridge Protocol Data Units on said transmissionpaths.
 7. A network as claimed in claim 6 wherein said auto-discoverymechanism is a Virtual Private Local Area Network Service auto-discoverymechanism.
 8. A network as claimed in claim 3 wherein said provider edgedevices are network-facing provider edge devices.